Skip to content

fix: Implement networkOnly.handle using cloned context with Edge#22975

Closed
TatuLund wants to merge 3 commits intomainfrom
fix-22954
Closed

fix: Implement networkOnly.handle using cloned context with Edge#22975
TatuLund wants to merge 3 commits intomainfrom
fix-22954

Conversation

@TatuLund
Copy link
Contributor

@TatuLund TatuLund commented Dec 12, 2025

With cloned context Edge browser seems not to get stuck

Fixes #22954

See: https://github.com/WICG/service-worker-auto-preload?tab=readme-ov-file#how-it-works

Added a timeout to the fetch request to prevent it from getting stuck indefinitely in Edge.
@github-actions
Copy link

github-actions bot commented Dec 12, 2025

Test Results

1 308 files  ±0  1 308 suites  ±0   1h 16m 0s ⏱️ -46s
9 196 tests ±0  9 128 ✅ ±0  68 💤 ±0  0 ❌ ±0 
9 652 runs   - 1  9 576 ✅  - 1  76 💤 ±0  0 ❌ ±0 

Results for commit b1335eb. ± Comparison against base commit f1cdf43.

♻️ This comment has been updated with latest results.

@TatuLund TatuLund closed this Dec 12, 2025
@TatuLund TatuLund reopened this Dec 12, 2025
Refactor fetch handling to improve reliability in Edge.
@TatuLund TatuLund changed the title fix: Implement fetch timeout for network requests fix: Implement network.Only using cloned context with Edge Dec 12, 2025
@TatuLund TatuLund changed the title fix: Implement network.Only using cloned context with Edge fix: Implement networkOnly.handle using cloned context with Edge Dec 12, 2025
@sonarqubecloud
Copy link

@TatuLund TatuLund marked this pull request as ready for review December 12, 2025 12:09
@caalador
Copy link
Contributor

Seems like this fix is not needed as the latest version 143.0.3650.80 doesn't have the problem noted in the ticket.

@mshabarov
Copy link
Contributor

@TatuLund do you think we can close this PR in favor of patch made in Edge?

@TatuLund
Copy link
Contributor Author

I would hope so. Lets follow-up few days if the need for this indeed has been deprecated.

@mcollovati
Copy link
Collaborator

I would hope so. Lets follow-up few days if the need for this indeed has been deprecated.

@TatuLund any updates on this? Can we close the PR?

@TatuLund
Copy link
Contributor Author

TatuLund commented Jan 9, 2026

Can we close the PR?

Yes, lets close. This should be fixed in Chrome.

@TatuLund TatuLund closed this Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Blank Screen after Microsoft EDGE Update 143 (PWA)

4 participants